GPS Renewables Change Document · Maintenance Management Platform
Confidential · Internal Version 1.0 · 10 July 2026
Change Document

Maintenance Management Platform

Current design build compared against the Design Brief v1.0
Document typeChange document (design build vs. approved brief)
BaselineDesign Brief — Maintenance Management Platform v1.0 (08 Jul 2026), companion to SRS Draft v0.1
Compared artefactInteractive design build — Maintenance Platform.dc.html (with RequestBody and Chatter)
Version1.0
Date10 July 2026

1. Purpose & How To Read This

This document records where the current design build agrees with the Design Brief, where it intentionally deviates, and what remains open. It is organised by the brief's own screen inventory (S1–S13) and component list so every line traces back to a requirement. SRS requirement IDs are shown as FR-XX-00.

Status is expressed with these tokens:

BUILT  Matches the brief MODIFIED  Built, but deviates by decision PARTIAL  Partly built OPEN  Not yet built DESCOPED  Removed by decision

2. Changes Applied This Cycle

Decisions taken after the brief was approved, and applied to the build.

AreaChangeReasonStatus
UsersEach user now carries exactly one Discipline, chosen from a central list. Skill-tag (many-per-user) model dropped.One user, one disciplineMODIFIED
Users & TeamsTeams reinstated. Screen is now a two-tab table (Users / Teams). Teams support create and delete.Team creation requestedBUILT
Team membershipMany-to-many: a user can be in more than one team. Editable both ways — from a user (assign teams) and from a team (add / remove members). Restricted to Site Manager and Admin.Stakeholder requestBUILT
DisciplinesDisciplines defined centrally under Tags, editable by Central Admin only.Central definitionBUILT
RolesRole set changed to Operations Lead (Central), Maintenance Lead (Central), Site Manager, Product Owner, Technical Lead.Stakeholder requestMODIFIED
AccessStandalone Access screen/section removed.Not requiredDESCOPED
Maintenance Plan"Preventive" renamed Maintenance Plan and moved under the Configure group.Placement requestMODIFIED
RecurrencePM recurrence reworked to Odoo style: Recurrent toggle, "Repeat every N Days/Weeks/Months/Years", Ends Forever / Until date.Match Odoo patternBUILT
PM Plan formTeam made mandatory; Discipline added as optional selector.Stakeholder requestBUILT
Activity createScheduled date added as a required field with a native date picker.Emphasis on schedule dateBUILT
Activity detailScheduled date emphasised; Request date and Requested by demoted to secondary info.Reviewer commentBUILT
Detail layoutSplit / Tabs switcher removed; detail is always the split (side-panel) layout.Single layoutDESCOPED
Activity logFollower avatars, Follow / Unfollow and the "followers" count removed from Chatter and the detail header.Reviewer commentDESCOPED
Site & AreasArea delete is available only when no equipment is assigned to that area.Data-integrity guardBUILT

3. Requirement Coverage By Screen

Against the brief's screen inventory (Section 3).

#ScreenStatusNotes
S1Sign-in (SSO hand-off)OPENNo Keycloak hand-off screen built yet. NFR-SEC-01
S2DashboardPARTIALSite dashboard with KPI strip and charts built. Portfolio and Central read-only variants not yet drawn. FR-RPT-01/02/03
S3Requests board (Kanban)BUILTBoard / List / Calendar toggle, stage columns, card badges, linked-pair icon. Labelled "Activities". FR-LC-01, FR-CAL-05
S4Request detailBUILTSplit record + activity log. Scheduled date emphasised. Followers removed (see §4). FR-CM-02, FR-LC-02/05
S5Raise corrective requestBUILTGuided create modal with equipment, problem, priority, immediate flag, team, scheduled date. FR-CM-01/04
S6Maintenance calendarBUILTMonth calendar of scheduled work with filter bar. FR-CAL-01
S7Equipment registerBUILTList filtered by area and tag. FR-EQ-04/09
S8Equipment detailBUILTOverview / Reliability / History / Documents / Activity tabs. FR-EQ-02/06/07/10
S9Preventive setupMODIFIEDBuilt as "Maintenance Plan" under Configure; Odoo-style recurrence. FR-PM-01/02/03
S10Reports & analyticsOPENNav entry present; screen is a placeholder. Charts/export/scope not built. FR-RPT-04/05/06
S11Site & area configurationBUILTSite details + area list; area delete guarded by equipment count. FR-SITE-01/07
S12Users, teams & skillsMODIFIEDBuilt as "Users & Teams" (tabbed). Teams reinstated with many-to-many membership, editable both ways. Skill-tags replaced by one Discipline per user (see §4). FR-USR-01/04/06
S13Stages configurationBUILTOrdered stage set with closing stage. FR-LC-08

4. Deviations From The Brief

Where the build intentionally departs from the approved brief. Each carries a requirement impact to confirm.

DeviationBrief saidBuild doesRequirement impact
Skill tags → DisciplineManage skill tags on engineers from a managed list; multiple per engineer.One discipline per user, from a central list.FR-USR-06 re-interpreted
Followers removedChatter shows follower avatars + follow / unfollow; following drives notifications.Followers and follow controls removed.FR-NOT-02
Role setAccess matrix roles: Ops, Engineer, Site Mgr, Portfolio Mgr, Central, Admin.Operations Lead, Maintenance Lead, Site Manager, Product Owner, Technical Lead.§5, FR-ACC-01–06
Access sectionRole-based UI expressed by removing controls per role.Standalone Access section removed; role gating retained in code.FR-ACC-05
PM placement"Preventive" as a top-level operations screen."Maintenance Plan" under the Configure group.Navigation only
Detail layoutDocked panel on desktop, switchable tab on mobile.Split layout only; layout switcher removed.Presentation only

5. Open Gaps

In the brief, not yet in the build.

ItemWhat is missingRequirement
Sign-in (SSO)Branded Keycloak hand-off screen.NFR-SEC-01
Reports & analyticsKPI/chart screen with group-by, export and role scope. Currently a placeholder.FR-RPT-04/05/06
Dashboard variantsPortfolio (read-only roll-up) and Central (all-sites compare) dashboards.FR-RPT-01/02
Read-only role statesPortfolio / Central screens drawn without any write affordances.FR-ACC-05
Close-out detailConfirm the pre-fill rule (elapsed candidates, discard ≤10 min, lowest) is fully represented. Modal exists.FR-LC-10/11
Empty / error statesSystematic empty, loading and no-access states across lists.NFR-USE-01

6. Traceability Impact

Requirements whose status changed as a result of this cycle's decisions. All others remain as mapped in Brief Section 9.

RequirementConcernsNew status
FR-USR-04Place users on teamsMet — many-to-many team membership
FR-USR-06Skill tags on engineersReplaced by single Discipline
FR-LC-03Team assignment / shared visibilityTeam model restored; confirm visibility rule
FR-NOT-02Following controls who is notifiedAt risk — followers removed
FR-ACC-01–06Role-based access modelRe-scoped — role set changed
To confirm: Team membership is now many-to-many; confirm whether team assignment still grants shared record visibility (FR-LC-03). Removing followers still affects notification routing (FR-NOT-02) — decide whether notifications route by team / discipline / direct assignee, and update the SRS accordingly so traceability stays intact.

7. Approvals

This change document is confirmed by:

RoleResponsibilityName / Sign-off
Operations Lead (Central)Confirms operations workflows and cross-site oversight needs—
Maintenance Lead (Central)Confirms maintenance workflows, disciplines, and KPIs—
Site Manager (representative)Confirms site-level configuration and access model—
Product OwnerOwns scope, priorities, and acceptance—
Technical LeadConfirms feasibility; owns the follow-on technical design—

End of change document v1.0 — companion to Design Brief v1.0 and SRS Draft v0.1